| Package | hl7.ehrs.uv.phrsfmr2 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-S.4.5.html |
| Url | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-S.4.5 |
| Version | 2.0.1-ballot |
| Status | active |
| Date | 2025-04-03T15:15:30+00:00 |
| Name | S_4_5_Manage_PHR_Account_Holder_Reminder_Information_Updates |
| Title | S.4.5 Manage PHR Account Holder Reminder Information Updates (Function) |
| Experimental | False |
| Authority | hl7 |
| Description | Receive and validate formatted inbound communications to facilitate updating of PHR Account Holder reminder information from external sources such as Cancer or Immunization Registries. |
| Purpose | Information from outside groups, such as immunization groups or public health organizations, may periodically have and send updates of value to PHR Account Holders. The system should be capable of generating reminders based on the recommendations of these organizations. Reminders could be provided to PHR Account Holders by a number of means, including alerts or system generated email. A record of such reminders may become part of a PHR Account Holder’s record. Example(s): Reminders could include a recommended immunization, prophylactic guidelines for treating Mitral Valve Prolapse disorder, or PHR Account Holder self-testing for disease. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Receive and validate formatted inbound communications to facilitate updating of PHR Account Holder reminder information from external sources such as Cancer or Immunization Registries.
Information from outside groups, such as immunization groups or public health organizations, may periodically have and send updates of value to PHR Account Holders. The system should be capable of generating reminders based on the recommendations of these organizations. Reminders could be provided to PHR Account Holders by a number of means, including alerts or system generated email. A record of such reminders may become part of a PHR Account Holder’s record.
Example(s): Reminders could include a recommended immunization, prophylactic guidelines for treating Mitral Valve Prolapse disorder, or PHR Account Holder self-testing for disease.
| S.4.5#01 | SHOULD |
The system SHOULD provide the ability to automatically receive inbound communications from external sources (e.g., from Cancer Registries or Immunization Registries) to facilitate updating of the PHR Account Holder's reminder-related information. |
| S.4.5#02 | conditional SHOULD |
IF the system has received an inbound communication from an external source (e.g., from Cancer Registry or Immunization Registry) regarding reminder-related information, THEN the system SHOULD provide the ability for the PHR Account Holder to transmit an acknowledgement of that inbound communication. |
| S.4.5#03 | conditional SHOULD |
IF the system has received inbound communications from external sources (e.g., from Cancer Registries or Immunization Registries) regarding reminder-related information, THEN the system SHOULD provide the ability for the PHR Account Holder to maintain that reminder-related information (e.g., by reviewing, editing, storing, harmonizing, updating, or deleting the information). |
| S.4.5#04 | MAY |
The system MAY provide the ability to manage reminders automatically for PHR Account Holders meeting specific criteria (e.g., age, gender, or diagnosis). For example, the PHR Account Holder is a male and does not need to view reminders about annual mammograms; or the PHR Account Holder is diabetic and desires to receive and store reminders about foot examinations that will help assess circulatory health. |
| S.4.5#05 | MAY |
The system MAY provide the ability to render reminders automatically to the PHR Account Holder (e.g., via email or voice message). |
| S.4.5#06 | SHOULD |
The system SHOULD log reminder activity (e.g., by logging the fact the PHR-S transmitted a reminder message to the PHR Account Holder's email or mobile phone regarding an upcoming appointment). |
FHIR{
"resourceType" : "Requirements",
"id" : "PHRSFMR2-S.4.5",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Receive and validate formatted inbound communications to facilitate updating of PHR Account Holder reminder information from external sources such as Cancer or Immunization Registries.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Information from outside groups, such as immunization groups or public health organizations, may periodically have and send updates of value to PHR Account Holders. The system should be capable of generating reminders based on the recommendations of these organizations. Reminders could be provided to PHR Account Holders by a number of means, including alerts or system generated email. A record of such reminders may become part of a PHR Account Holder’s record.</p>\n<p>Example(s): Reminders could include a recommended immunization, prophylactic guidelines for treating Mitral Valve Prolapse disorder, or PHR Account Holder self-testing for disease.</p>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.4.5#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to automatically receive inbound communications from external sources (e.g., from Cancer Registries or Immunization Registries) to facilitate updating of the PHR Account Holder's reminder-related information.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.4.5#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF the system has received an inbound communication from an external source (e.g., from Cancer Registry or Immunization Registry) regarding reminder-related information, THEN the system SHOULD provide the ability for the PHR Account Holder to transmit an acknowledgement of that inbound communication.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.4.5#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF the system has received inbound communications from external sources (e.g., from Cancer Registries or Immunization Registries) regarding reminder-related information, THEN the system SHOULD provide the ability for the PHR Account Holder to maintain that reminder-related information (e.g., by reviewing, editing, storing, harmonizing, updating, or deleting the information).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.4.5#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage reminders automatically for PHR Account Holders meeting specific criteria (e.g., age, gender, or diagnosis). For example, the PHR Account Holder is a male and does not need to view reminders about annual mammograms; or the PHR Account Holder is diabetic and desires to receive and store reminders about foot examinations that will help assess circulatory health.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.4.5#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to render reminders automatically to the PHR Account Holder (e.g., via email or voice message).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.4.5#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD log reminder activity (e.g., by logging the fact the PHR-S transmitted a reminder message to the PHR Account Holder's email or mobile phone regarding an upcoming appointment).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "ehr"
}
],
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-S.4.5",
"version" : "2.0.1-ballot",
"name" : "S_4_5_Manage_PHR_Account_Holder_Reminder_Information_Updates",
"title" : "S.4.5 Manage PHR Account Holder Reminder Information Updates (Function)",
"status" : "active",
"date" : "2025-04-03T15:15:30+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Receive and validate formatted inbound communications to facilitate updating of PHR Account Holder reminder information from external sources such as Cancer or Immunization Registries.",
"purpose" : "Information from outside groups, such as immunization groups or public health organizations, may periodically have and send updates of value to PHR Account Holders. The system should be capable of generating reminders based on the recommendations of these organizations. Reminders could be provided to PHR Account Holders by a number of means, including alerts or system generated email. A record of such reminders may become part of a PHR Account Holder’s record.\r\n\r\nExample(s): Reminders could include a recommended immunization, prophylactic guidelines for treating Mitral Valve Prolapse disorder, or PHR Account Holder self-testing for disease.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.4.5-01",
"label" : "S.4.5#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to automatically receive inbound communications from external sources (e.g., from Cancer Registries or Immunization Registries) to facilitate updating of the PHR Account Holder's reminder-related information."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.4.5-02",
"label" : "S.4.5#02",
"conformance" : [
"SHOULD"
],
"conditionality" : true,
"requirement" : "IF the system has received an inbound communication from an external source (e.g., from Cancer Registry or Immunization Registry) regarding reminder-related information, THEN the system SHOULD provide the ability for the PHR Account Holder to transmit an acknowledgement of that inbound communication."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.4.5-03",
"label" : "S.4.5#03",
"conformance" : [
"SHOULD"
],
"conditionality" : true,
"requirement" : "IF the system has received inbound communications from external sources (e.g., from Cancer Registries or Immunization Registries) regarding reminder-related information, THEN the system SHOULD provide the ability for the PHR Account Holder to maintain that reminder-related information (e.g., by reviewing, editing, storing, harmonizing, updating, or deleting the information)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.4.5-04",
"label" : "S.4.5#04",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage reminders automatically for PHR Account Holders meeting specific criteria (e.g., age, gender, or diagnosis). For example, the PHR Account Holder is a male and does not need to view reminders about annual mammograms; or the PHR Account Holder is diabetic and desires to receive and store reminders about foot examinations that will help assess circulatory health."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.4.5-05",
"label" : "S.4.5#05",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to render reminders automatically to the PHR Account Holder (e.g., via email or voice message)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.4.5-06",
"label" : "S.4.5#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD log reminder activity (e.g., by logging the fact the PHR-S transmitted a reminder message to the PHR Account Holder's email or mobile phone regarding an upcoming appointment)."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.